Skip to content

feat: add Claude Code plugin manifest#462

Merged
miguel-heygen merged 4 commits intomainfrom
worktree-feat+claude-code-plugin
Apr 23, 2026
Merged

feat: add Claude Code plugin manifest#462
miguel-heygen merged 4 commits intomainfrom
worktree-feat+claude-code-plugin

Conversation

@miguel-heygen
Copy link
Copy Markdown
Collaborator

@miguel-heygen miguel-heygen commented Apr 23, 2026

Summary

  • add the repo-root Claude Code plugin manifest at .claude-plugin/plugin.json, alongside the existing Codex plugin surface
  • document Claude Code usage in README.md next to the Codex install note
  • add Claude marketplace submission assets at assets/claude-code-icon-dark.svg and assets/claude-code-icon-light.svg
  • brand the plugin description as HyperFrames by HeyGen
  • document that Claude Code auto-discovers the root skills/ directory when the manifest omits a skills field
  • use black/white Claude marketplace icon assets for the two theme slots

Diff

  • .claude-plugin/plugin.json
  • README.md
  • assets/claude-code-icon-dark.svg
  • assets/claude-code-icon-light.svg

Verification

  • claude plugin validate .

Notes

  • Claude Code's repo-side schema rejects displayName, title, icon, and logo, so the explicit marketplace title/icon choice is documented in-repo for submission rather than encoded in plugin.json.
  • assets/claude-code-icon-dark.svg now uses a black background and assets/claude-code-icon-light.svg uses a white background.
  • The branch lives in the dedicated worktree at /Users/miguel07code/dev/hyperframes-oss/.claude/worktrees/feat+claude-code-plugin for any follow-up fixes.

@miguel-heygen miguel-heygen changed the title [codex] Add Claude Code plugin manifest feat: add Claude Code plugin manifest Apr 23, 2026
@miguel-heygen miguel-heygen marked this pull request as ready for review April 23, 2026 20:24
Copy link
Copy Markdown
Collaborator

@jrusso1020 jrusso1020 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: approve

Clean port of the Codex/Cursor pattern. Structure matches: in-repo manifest at .claude-plugin/plugin.json alongside .codex-plugin/ and (inbound in #461) .cursor-plugin/, README addendum next to the Codex install note, marketplace-visible branding through the description field.

Schema compliance looks right. I spot-checked the Claude Code plugin manifest schema — the 7 fields you include (name / description / version / author / homepage / repository / license) are all valid; displayName / title / icon / logo are indeed rejected, so the in-README submission notes are the right place for them.

Skill discovery is actually wired correctly — but subtly: when a manifest is present without a skills field (your case), Claude Code falls back to the default skills/ directory at the plugin root. That works for us because the repo already ships skills/ at root (shared with Codex + Cursor) so all five SKILL.md files get picked up automatically. Worth a single-line note somewhere — the manifest or the README — saying "Claude Code auto-discovers skills/ by convention when the manifest omits the field" so the next maintainer doesn't wonder why Codex points at ./skills/ explicitly but the Claude manifest doesn't. Non-blocking.

"HyperFrames by HeyGen" naming + white-bg icons line up with what just shipped in #461 + the openai/plugins branding refresh → the three plugin surfaces will read as the same product.

Two non-blocking notes:

  1. Dark and light SVGs are byte-identical. Both have <rect width="100" height="100" fill="white"/> + the same two gradient paths. That's consistent with the Codex/Cursor "white bg everywhere" decision James made today, so functionally it's fine. But the -dark / -light naming implies the marketplace submission form will present it as two theme-specific slots, and uploading identical files to both could look like a sub-pass on a reviewer. Options I'd consider before submission: (a) upload the same asset once if the form allows, (b) make -dark.svg actually dark-theme-appropriate (e.g. dark bg so the green-cyan gradient reads on a light theme after inversion), or (c) leave as-is and accept the "two identical uploads" shape. Worth a sanity check against the Claude marketplace submission UI.

  2. README merge conflict with #461. My Cursor plugin PR inserts a one-line addendum at the exact same position — right between the Codex codex plugin marketplace add ... block and the "Try it" section. Whichever of the two lands first will force a 1-line rebase on the other. I'd propose: let #461 (pending James's merge) land first since it also carries the "HyperFrames by HeyGen" title update + the asset swap, then rebase this; the rebase is trivially "move your insertion one line down past the Cursor block". Or the other way around — either is fine, just flagging so we don't both push into a conflict.

No blockers. Skills, pattern, schema all line up. Ship on James's go-ahead.


Review by hyperframes

Adds .claude-plugin/plugin.json so the repo can be loaded as a Claude
Code plugin. Reuses the existing skills/ directory — all 5 skills
(hyperframes, gsap, hyperframes-cli, hyperframes-registry,
website-to-hyperframes) are auto-discovered under the hyperframes:
namespace.
@miguel-heygen miguel-heygen force-pushed the worktree-feat+claude-code-plugin branch from 9500b2c to 2d34c9f Compare April 23, 2026 21:02
@miguel-heygen miguel-heygen merged commit 1545112 into main Apr 23, 2026
24 checks passed
@miguel-heygen miguel-heygen deleted the worktree-feat+claude-code-plugin branch April 23, 2026 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants